Systems and methods to facilitate nesting of portfolios within a collaboration environment

ABSTRACT

Systems and methods to facilitate nesting of portfolios within a collaboration environment are described herein. Exemplary implementations may: manage environment state information maintaining a collaboration environment; obtain hierarchical information for work unit records, project records, and/or portfolio records; update the environment state information based on the role information; specify nested portfolio hierarchical information specific to the portfolio records and specifying individual portfolio records as being subordinate to other individual ones of the portfolio records; effectuate presentation of portfolio pages for the portfolio records within a user interface of the collaboration environment; and/or perform other operations.

FIELD OF THE DISCLOSURE

The present disclosure relates to systems and methods to facilitatenesting of portfolios within a collaboration environment.

BACKGROUND

Collaboration environments, sometimes referred to as work managementplatforms, may enable users to assign projects, tasks, or otherassignments to assignees (e.g., other users) to complete. Acollaboration environment may comprise an environment in whichindividual users and/or a virtual team of users does its work and mayenable users to work in a more organized and efficient manner. Projectsmay be a way to organize groups of tasks. Portfolios may be a way toorganize groups of projects.

SUMMARY

One aspect of the present disclosure relates to a system configured tofacilitate nesting of portfolios within a collaboration environment. Thecollaboration environment may specify a multi-tiered, hierarchicalarrangement, with respect to one or more of portfolios, projects, unitsof work, and/or other items that make up the collaboration environment.A portfolio may include one or more projects subordinate to theportfolio and/or that make up the portfolio. A project may include oneor more units of work subordinate to the project, that make up theproject, and/or otherwise support the project. A unit of work mayinclude an action item a user should carry out outside and/or within thecollaboration environment. Traditionally, the hierarchy of portfolios,projects, units of work, and/or other items may create a rigidorganization of information within the collaboration environment. Forexample, this organization may create a hardline top-down approach toaccess information, e.g., starting from portfolios, then to projectscontained with the portfolios, and then to units of work containedwithin the projects. Some users may find the rigidity of this type oforganization helpful due to its precision, while other users may find itdifficult for these same reasons. For example, these hierarchies may notalign with how some users organize, which may follow a more intuitiveapproach rather than this hardline rigid approach. Some problems maystem from a concept of the portfolios being rigidly fixed at the toplevel of these hierarchies. One or more implementations of the systemsand method presented herein propose a solution where portfolios may beadded to other portfolios, e.g., portfolios may be “nested” within otherportfolios. This may create a nesting effect of the portfolios where agiven portfolio may include one or more other portfolios that areconsidered “subordinate” to the given portfolio. This may eliminate therestriction of portfolios being solely fixed atop the hierarchies. Now,users may organize sets of portfolios in a way that can reflect howtheir teams are structured, and seamlessly monitor and communicate thehealth of work. The nested portfolios may allow companies to organizetheir work to represent different perspectives of the work, which wouldotherwise require tedious and disruptive navigation through seeminglyendless hierarchies. In some implementations, an individual portfoliomay be “multi-homed,” meaning the individual portfolio may be nestedwithin more than one other portfolio.

One or more implementations of a system to facilitate nesting ofportfolios within a collaboration environment may include one or morehardware processors configured by machine-readable instructions and/orother components. Executing the machine-readable instructions may causethe one or more hardware processors to facilitate interaction with acollaboration environment based on assignment of project-level roles.The machine-readable instructions may include one or more computerprogram components. The one or more computer program components mayinclude one or more of an environment state component, an organizationcomponent, a user interface component, and/or other components.

The environment state component may be configured to manage environmentstate information maintaining a collaboration environment and/or otherinformation. The collaboration environment may be configured tofacilitate interaction by users with the collaboration environment. Theenvironment state information may define one or more of work unitrecords, project records, portfolio records, and/or other records. Thework unit records may include work unit information associated withunits of work managed, created, and/or assigned within the collaborationenvironment. The project records may include project informationassociated with projects managed, created, and/or assigned within thecollaboration environment. The portfolio records may include portfolioinformation associated with portfolios managed within the collaborationenvironment.

The organization component may be configured to obtain hierarchicalinformation for the records of the collaboration environment. Thehierarchical information may include information for the work unitrecords, the project records, and the portfolio records, and/or nestedportfolio hierarchical information specific to the portfolio records.The hierarchical information may specify one or more of individual workunit records as subordinate to individual project records, theindividual project records as subordinate to individual portfoliorecords, and/or other specifications. In some implementations, anindividual project record may include one or more work unit records byvirtue of the one or more work unit records being subordinate to theindividual project record. An individual portfolio record may includeone or more project records by virtue of the one or more project recordsbeing subordinate to the individual portfolio record. By way ofnon-limiting illustration, a first work unit record may be subordinateto a first project record and/or other project records. The firstproject record may be subordinate to a first portfolio record and/orother portfolio records.

The nested portfolio hierarchical information may specify thatindividual portfolio records are subordinate to other individual ones ofthe portfolio records. By way of non-limiting illustration, the nestedportfolio hierarchical information may specify a second portfolio recordas being subordinate to the first portfolio record.

The user interface component may be configured to effectuatepresentation of views of the collaboration environment based on one ormore of the environment state information, the hierarchical information,and/or other information. In some implementations, user interfacecomponent may be configured to effectuate presentation of portfoliopages for the portfolio records within a user interface of thecollaboration environment. The individual portfolio pages for theindividual portfolio records may provide access to individual projectrecords and/or other individual portfolio records that may besubordinate to the individual portfolio records. By way of non-limitingillustration, a first portfolio page for the first portfolio record mayprovide access to one or more of the first project record specified assubordinate to the first portfolio record, the second portfolio recordspecified as subordinate to the first portfolio record, and/or otherrecords.

As used herein, any association (or relation, or reflection, orindication, or correspondency) involving servers, processors, clientcomputing platforms, and/or another entity or object that interacts withany part of the system and/or plays a part in the operation of thesystem, may be a one-to-one association, a one-to-many association, amany-to-one association, and/or a many-to-many association or N-to-Massociation (note that N and M may be different numbers greater than 1).

These and other features, and characteristics of the present technology,as well as the methods of operation and functions of the relatedelements of structure and the combination of parts and economies ofmanufacture, will become more apparent upon consideration of thefollowing description and the appended claims with reference to theaccompanying drawings, all of which form a part of this specification,wherein like reference numerals designate corresponding parts in thevarious figures. It is to be expressly understood, however, that thedrawings are for the purpose of illustration and description only andare not intended as a definition of the limits of the invention. As usedin the specification and in the claims, the singular form of “a”, “an”,and “the” include plural referents unless the context clearly dictatesotherwise.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a system configured to facilitate nesting ofportfolios within a collaboration environment, in accordance with one ormore implementations.

FIG. 2 illustrates a method to nest portfolios within a collaborationenvironment, in accordance with one or more implementations.

FIG. 3 illustrates a user interface, in accordance with one or moreimplementations.

FIG. 4 illustrates a user interface, in accordance with one or moreimplementations.

DETAILED DESCRIPTION

FIG. 1 illustrates a system 100 configured to facilitate nesting ofportfolios within a collaboration environment, in accordance with one ormore implementations. The collaboration environment may specify amulti-tiered, hierarchical arrangement, with respect to one or more ofportfolios, projects, units of work, and/or other items that make up thecollaboration environment. Traditionally, the hierarchy of portfolios,projects, units of work, and/or other items may create a rigidorganization of information within the collaboration environment suchthat portfolios are affixed solely atop the hierarchy. One or moreimplementations presented herein propose “nesting” portfolios withinother portfolios. This may eliminate a restriction of portfolios beingsolely fixed atop the hierarchies. Now, users may organize sets ofportfolios in a way that can reflect how their teams are structured, andseamlessly monitor and communicate the health of work. In someimplementations, an individual portfolio may be “multi-homed,” meaningthe individual portfolio may be nested within more than one otherportfolio.

In some implementations, system 100 may include one or more of one ormore servers 102, one or more client computing platforms 104, externalresources 126, and/or other components. Server(s) 102 may be configuredto communicate with one or more client computing platforms 104 accordingto a client/server architecture and/or other architectures. Clientcomputing platform(s) 104 may be configured to communicate with otherclient computing platforms via server(s) 102 and/or according to apeer-to-peer architecture and/or other architectures. Users may accesssystem 100 via client computing platform(s) 104.

Server(s) 102 may include one or more of non-transitory electronicstorage 128, one or more processors 130 configured by machine-readableinstructions 106, and/or other components. The non-transitory electronicstorage 128 may store one or more records and/or other information.Machine-readable instructions 106 may include one or more instructioncomponents. The instruction components may include computer programcomponents. Executing the machine-readable instructions 106 may causeserver(s) 102 to facilitate nesting of portfolios within a collaborationenvironment. The computer program components may include one or more ofan environment state component 108, an organization component 110, auser interface component 112, and/or other components.

Environment state component 108 may be configured to manage environmentstate information and/or other information used in maintaining acollaboration environment. The collaboration environment may beconfigured to facilitate interaction by users within the collaborationenvironment. The environment state information may include one or moreof user records, work unit records, project records, portfolio records,objective records, and/or other records. The user records may includeuser information comprising values of user parameters. The work unitrecords which may include work information comprising values for workunit parameters associated with units of work managed, created, and/orassigned within the collaboration environment. The project records mayinclude project information associated with projects managed, created,and/or assigned within the collaboration environment. The portfoliorecords including portfolio information associated with portfoliosmanaged within the collaboration environment. The objective records mayinclude objective information associated with business objectivesmanaged, created, and/or owned within the collaboration environment.

The user information in the user records may include values of userparameters. The values of the user parameters may be organized in userrecords corresponding to users interacting with and/or viewing thecollaboration environment. The values of the user parameters may includeinformation describing the users, their actions within the collaborationenvironment, their settings, and/or other user information; and/ormetadata associated with the users, their actions within theenvironment, their settings, and/or other user information. Individualones of the users may be associated with individual ones of the userrecords. A user record may define values of the user parametersassociated with a given user.

The values of the user parameters may, by way of non-limiting example,specify one or more of: a user name, a group parameter, a user account,a user department, descriptive user content, a to-email, a from-email, aphoto, an organization, a workspace, one or more user comments, one ormore teams the user belongs to, one or more of the user display settings(e.g., colors, size, project order, task order, other unit of workorder, etc.), one or more authorized applications, one or moreinteraction parameters (e.g., indicating a user is working on/worked ona given unit of work, a given user viewed a given work unit of work, agiven user selected a given unit of work, a timeframe a given user lastinteracted with and/or worked on a given unit of work, a time periodthat a given unit of work has been idle, and/or other interactionparameters), one or more notification settings, one or more progressparameters, status information for one or more work units the user isassociated with (units of work assigned to the user, assigned to otherusers by the user, completed by the user, past-due date, and/or otherinformation), progress information for one or more business objectivesthe user is associated with (business objectives owned by the user, ofwhich the user is a collaborator, fulfilled by the user, past-due date,and/or other information), one or more performance/productivity metricsof a given user (e.g., how many units of work the user has completed,how quickly the user completed the units of work, how quickly the usercompletes certain types of work units, the efficiency of the user,bandwidth of the user, activity level of the user, how many businessobjectives the user has helped fulfill through their completion of unitsof work, etc.), application access information (e.g., username/passwordfor one or more third-party applications), one or more favorites and/orpriorities, preference information, and/or other information.

The work information in the work unit records may include values of oneor more work unit parameters. The values of the work unit parameters maybe organized in work unit records corresponding to units of workmanaged, created, and/or assigned within the collaboration environment.A given unit of work may have one or more assignees and/or collaboratorsworking on the given work unit. Units of work may include one or moreto-do items, action items, and/or other units of work one or more usersshould accomplish and/or plan on accomplishing. Units of work may becreated by a given user for the given user and/or created by the givenuser and assigned to one or more other users. Individual units of workmay include one or more of an individual task, an individual sub-task,and/or other units of work assigned to and/or associated with one ormore users. Individual units of work may include one or more digitalcontent items. An individual unit of work may include an individualdigital content item by virtue of the individual digital content item(and/or a copy or instance thereof) being attached and/or appendedthereto. A digital content item may include one or more of an image, avideo, an audio file, a PDF, a word document, and/or other digitalcontent items.

In some implementations, units of work created by, assigned to, and/orcompleted by the users may refer generally to a linking of the units ofwork with the individual users in the collaboration environment. A unitof work may be linked with a user in a manner that defines one or morerelationships between the user and the unit of work. Such a relationshipmay connote and/or be a result of an action (past, present, and/orfuture) of the user with respect to the unit of work. Such actions mayinclude one or more of creating a work unit record for a unit of work,being assigned to participate in a unit of work, participating in a unitof work, being granted access to a work unit record of a unit of work,adjusting a value of a work unit parameter of a work unit record of aunit of work, and/or other actions.

In some implementations, the one or more work unit parameters mayinclude one or more of a work assignment parameter, a work managementparameter, work creation parameter, and/or other parameters. The valuesof the work assignment parameter may describe units of work assigned tothe individual users. The values of the work management parameter maydescribe units of work managed by the individual users. The values ofthe work creation parameter may describe units of work created by theindividual users.

In some implementations, values of work unit parameters may include oneor more of a unit of work name, a unit of work description, one or moreunit of work dates (e.g., a start date, a due date or end date, acompletion date, and/or dates), role information, a status parameter(e.g., an update, a hardcoded status update, a completed/incomplete/markcomplete, a measured status, a progress indicator, quantity of sub-workunits remaining for a given unit of work, measure of urgency, and/orother status parameter), one or more user comment parameters (e.g.,permission for who may make comments such as an assignee, an assignor, arecipient, one or more followers, and/or one or more other interestedparties; content of the comments; one or more times; presence or absenceof the functionality of up-votes; one or more hard-coded responses;and/or other parameters), one or more interaction parameters (e.g.,indicating a given unit of work is being worked on/was worked on, agiven work unit of work was viewed, a given unit of work was selected,how long the given unit of work has been idle, a last interactionparameter indicating when and what user last interacted with the givenunit of work, users that interacted with the given unit of work,quantity and/or content of comments on the unit of work, and/or otherinteraction parameters indicating sources of the interactions, contextof the interactions, content of the interactions and/or time for theinteractions), one or more digital content item attachments,notification settings, privacy, an associated URL, one or moreinteraction parameters (e.g., sources of the interactions, context ofthe interactions, content of the interactions, time for theinteractions, and/or other interaction parameters), updates, ordering ofunits of work within a given unit of work (e.g., tasks within a project,subtasks within a task, etc.), state of a workspace for a given unit ofwork (e.g., application state parameters, application status,application interactions, user information, and/or other parametersrelated to the state of the workspace for a unit of work), one or moreperformance/productivity metrics for a given unit of work, hierarchicalinformation (see, e.g., organization component 110), permissionsinformation (see, e.g., organization component 110), one or more customfields (e.g., priority, cost, stage, and/or other custom fields), and/orother information.

The values of the work assignment parameter describing units of workassigned to the individual users may be determined based on one or moreinteractions by one or more users with a collaboration environment. Insome implementations, one or more users may create and/or assign one ormore unit of work to themselves and/or another user. In someimplementations, a user may be assigned a unit of work and the user mayeffectuate a reassignment of the unit of work from the user or one ormore other users.

In some implementations, values of the work assignment parameter mayindicate that a status parameter of a unit of work has changed from“incomplete” to “marked complete” and/or “complete”. In someimplementations, a status of complete for a unit of work may beassociated with the passing of an end date associated with the unit ofwork. In some implementations, a status of “marked complete” may beassociated with a user providing input via the collaboration environmentat the point in time the user completes the unit of work (which may bebefore or after an end date).

In some implementations, managing by the environment state component 108include maintaining queues of the units of work assigned to the users.The queues may be presented to the users in a user interface of thecollaboration environment to facilitate access to the units of work viawork unit pages. A work unit page for a unit of work may comprise a userinterface portion and/or dedicated user interface of the collaborationenvironment from which users access the unit of work. Individual queuesmay represent the units of work assigned to individual users organizedin an order based on the individual end dates and/or other dates (e.g.,start dates) and/or other ordering. Individual queues may be presentedin a user interface based on one or more of a list view, a calendarview, and/or other views. The calendar view may be a calendar view byweek, by more than one week (e.g., 1st through 15th), by month, by morethan one month (e.g., May through July), and/or other calendar views.Units of work may be represented in a calendar view by user interfaceelements (e.g., icons, calendar entries, etc.).

Project information in project records may define values of projectparameters for projects managed within the collaboration environment. Anindividual project may include an individual set of the units of work.An individual set of units of work of an individual project may besubordinate to the individual project, make up the individual project,and/or otherwise support the individual project. The individual set ofunits of work may directly facilitate progress toward fulfillment of theindividual project. The individual set of units of work may directlycontribute to the progress. By way of non-limiting illustration, aconnection between the individual set of units of work and acorresponding individual project may be direct in that completion of atleast one of the units of work may have a direct impact on progresstoward fulfillment of the individual project. The concept of “directimpact” may mean that completion of the at least one unit of work maycause progress toward fulfillment of the individual project based onindependent action completed and/or started with respect to the at leastone unit of work. Accordingly, completion of an individual set of unitsof work may indicate that the individual project has been completedand/or fulfilled.

The project parameters may characterize one or more projects managedwithin the collaboration environment and/or via the collaborationenvironment, and/or the metadata associated with the one or moreprojects. Individual ones of the projects may be associated withindividual ones of the project records. The project information maydefine values of the project parameters associated with a given projectmanaged within the collaboration environment and/or via thecollaboration environment. A given project may have one or more ownersand/or one or more collaborators working on the given project. The givenproject may include one or more units of work assigned to one or moreusers under the given project heading. In some implementations, projectsmay include one or more units of work that may directly facilitateprogress toward fulfillment of the projects. Accordingly, completion ofthe set of units of work may directly contribute to progress towardfulfillment of the project. By way of non-limiting illustration, anindividual project may be associated with a client and the units of workunder the individual project heading may be work directly contributingto the fulfillment of a business relationship with the client.

The values of the project parameters may, by way of non-limitingexample, include one or more of: one or more units of work within theproject (which may include values of work unit parameters defined by oneor more work unit records), one or more user comment parameters (e.g., acreator, a recipient, one or more followers, one or more otherinterested parties, content, one or more times, upvotes, otherhard-coded responses, etc.), a project name, a project description, oneor more project dates (e.g., a start date, a due date, a completiondate, and/or other project dates), a status and/or progress (e.g., anupdate, a hardcoded status update, a measured status, quantity of unitsof work remaining in a given project, completed units of work in a givenproject, and/or other status parameter), one or more attachments,notification settings, privacy, an associated URL, one or moreinteraction parameters (e.g., sources of the interactions, context ofthe interactions, content of the interactions, time for theinteractions, and/or other interaction parameters), updates, ordering ofunits of work within the given project, hierarchical information (see,e.g., organization component 110), permissions information (see, e.g.,organization component 110), state of a workspace for a given taskwithin the given project, and/or other information.

Portfolio information in portfolio records may define values ofportfolio parameters for a portfolio managed within the collaborationenvironment. An individual portfolio may include one or more projectsand/or one or more other portfolios. A project of a portfolio may besubordinate to the portfolio, make up the portfolio, and/or otherwise beorganized within the heading of the portfolio.

The portfolio parameters may characterize portfolios managed within thecollaboration environment and/or via the collaboration environment,and/or the metadata associated with the portfolios. Individual ones ofthe portfolios may be associated with individual ones of the portfoliosrecords. The portfolio information may define values of the portfolioparameters associated with a given portfolio managed within thecollaboration environment and/or via the collaboration environment. Agiven portfolio may have one or more owners and/or one or morecollaborators working on the given portfolio. In some implementations, agiven portfolio may not have any owners and/or collaborators at theportfolio level other than those specified with respect to the projectssubordinate to the portfolio.

The values of the portfolio parameters may, by way of non-limitingexample, include and/or specify one or more of: information about one ormore projects within a given portfolio (which may include values ofproject parameters defined by one or more project records), informationabout one or more other portfolios within a given portfolio (which mayinclude values of portfolio parameters defined by one or more otherportfolio records), a portfolio name, a portfolio description, a statusand/or progress (e.g., an update, a hardcoded status update, a measuredstatus, quantity of units of work remaining in a given project,completed units of work in a given project, and/or other statusparameter), one or more attachments, notification settings, privacysettings, an associated URL, one or more interaction parameters (e.g.,sources of the interactions, context of the interactions, content of theinteractions, time for the interactions, and/or other interactionparameters), updates, ordering of projects within the given portfolio,hierarchical information (see, e.g., organization component 110),permissions information (see, e.g., organization component 110), stateof a workspace for a given project within the given portfolio, metadataassociated with the portfolios, custom fields (e.g., values created byusers), and/or other information.

The objective information in objective records may include values of oneor more objective parameters. The values of the objective parameters maybe organized in objective records corresponding to business objectivesmanaged, created, and/or owned within the collaboration environment. Agiven business objective may have one or more collaborators, and/or teammembers working on the given business objective. Business objectives mayinclude one or more associated units of work and/or projects one or moreusers should accomplish and/or plan on accomplishing. Businessobjectives may be created by a given user for the given user and/orcreated by the given user and assigned to be owned to one or more otherusers. Individual business objectives may include one or more of anindividual goal, an individual sub-goal, and/or other businessobjectives assigned to be owned by a user and/or associated with one ormore users.

The business objectives may be associated with a set of units of workand/or projects that may indirectly facilitate progress towardfulfillment of the business objectives. The set of units of work and/orprojects may not directly contribute to the progress. By way ofnon-limiting illustration, a connection between the set of units of workand/or projects and a corresponding business objective may be indirectin that completion of at least one of the units of work and/or projectsmay have no direct impact on progress toward fulfillment of the businessobjective. The concept of “no direct impact” may mean that completion ofthe at least one unit of work and/or project may not cause progresstoward fulfillment of the business objective without independent actionoutside of the at least one unit of work and/or project. Instead, thefulfillment of the at least one unit of work and/or project may makesuch independent action more likely (e.g., through coercion, assistance,education, incentivization, reminder, etc.). However, in someimplementations, business objectives may be associated with a set ofunits of work and/or projects that may directly facilitate progresstoward fulfillment of the business objectives. Accordingly, completionof the set of units of work and/or projects may directly contribute tothe progress toward fulfillment. Business objectives may be associatedwith an objectives and key result (OKR) goal-setting framework. Businessobjectives may be specified on one or more of a team basis, organizationbasis, and/or other specifications. In some implementations, businessobjectives may be characterized as user objectives. The user objectivesmay be associated with a set of units of work and/or projects that mayindirectly (and/or directly) facilitate progress toward fulfillment ofthe user objectives. User objectives may be specified on an individualuser basis.

Individual objective records may describe individual business objectivesand/or identify sets of individual ones of the work unit records and/orproject records that specify the units of work and/or projects as beingassociated with the individual business objectives.

In some implementations, the one or more objective parameters mayinclude one or more of an objective definition parameter, an objectiveowner parameter, an objective management parameter, an objectivecreation parameter, an objective progress parameter, and/or otherparameters. The value of the objective definition parameter may describethe particular business objective. The values of the objective ownerparameter may describe business objectives assigned to be owned by anindividual user. The values of the objective management parameter maydescribe business objectives managed as collaborators by the individualusers. The values of the objective creation parameter may describebusiness objectives created by the individual users.

In some implementations, the business objectives may be described basedon one or more of a business objective name, a business objectivedescription, one or more business objective dates (e.g., a start date, adue date, and/or dates), one or more users associated with a businessobjective, progress information (e.g., an update, a hardcoded statusupdate, a measured status, a progress indicator, quantity valueremaining for a given business objective, completed work units in agiven project, and/or other progress information), one or moreinteraction parameters, notification settings, privacy, an associatedURL, one or more custom fields (e.g., priority, cost, stage, and/orother custom fields), and/or other information.

The values of the objective owner parameter describing businessobjectives owned by the individual users may be determined based on oneor more interactions by one or more users with a collaborationenvironment. In some implementations, one or more users may createand/or assign ownership of one or more business objectives to themselvesand/or another user. In some implementations, a user may be assigned toown a business objective and the user may effectuate a reassignment ofownership of the business objective from the user or one or more otherusers.

The organization component 110 may be configured to obtain hierarchicalinformation for the records that make up the collaboration environment.In some implementations, hierarchical information may be specified forthe different types of records individually, and/or for a group ofdifferent types of records. By way of non-limiting illustration,hierarchical information for a group of different types of records maycreate a hierarchical arrangement which dictates access to differentones of types of the records.

In some implementations, the hierarchical information may specify workunit hierarchies. A work unit hierarchy may convey individual positionsof work unit records (and their corresponding units of work) in a recordhierarchy comprising solely of work unit records. By way of non-limitingillustration, a position may specify one or more of a work unit recordbeing superior to another work unit record, a work unit record beingsubordinate to another work unit record, and/or other information. As aresult, individual work units of work in the individual sets of workunit records may be subordinate to other individual work unit records inthe individual sets of work unit records. For example, a work unitrecord may define a unit of work comprising a task, and a subordinatework unit record may define a unit of work comprising a sub-task to thetask. A record hierarchy may define a relationship between work unitrecords. A work unit record may have some restrictions placed on it byvirtue of having a subordinate work unit record, and vice versa. By wayof non-limiting illustration, a work unit record may be restricted fromaccess by one or more users unless and/or until a subordinate work unitrecord is completed and/or started.

In some implementations, the hierarchical information may specifymulti-record hierarchies. A multi-record hierarchy may convey individualpositions of different types of records within a record hierarchy. Byway of non-limiting illustration, multi-record hierarchy may conveyindividual positions of work unit records, project records, andportfolio records in a record hierarchy comprising the work unitrecords, the project records, and the portfolio records. By way ofnon-limiting illustration, the hierarchical information may specify thatindividual work unit records are subordinate to individual projectrecords. The hierarchical information may specify that individualproject records are subordinate to individual portfolio records. By wayof non-limiting illustration, an individual project record may includeone or more work unit records by virtue of the one or more work unitrecords being subordinate to the individual project record. Anindividual portfolio record may include one or more project records byvirtue of the one or more project records being subordinate to theindividual portfolio record. By way of non-limiting illustration, thehierarchical information may specify a first work unit record may besubordinate to a first project record, and the first project record maybe subordinate to a first portfolio record.

In some implementations, hierarchical information may specify nestedportfolio hierarchical information specific to the portfolio records.The nested portfolio hierarchical information may specify thatindividual portfolio records are subordinate to other individual ones ofthe portfolio records. By way of non-limiting illustration, the nestedportfolio hierarchical information may specify a second portfolio recordas being subordinate to the first portfolio record. A record hierarchyspecific to the portfolio records may automatically define relationshipsbetween the portfolio records. A portfolio record may have somerestrictions placed on it by virtue of being subordinate to anotherportfolio record, and/or vice versa. By way of non-limitingillustration, a subordinate portfolio record may have accessrestrictions that conform to access restrictions of a superior portfoliorecord. This may allow users to nest portfolio records within otherportfolio records without worrying about violating permissions that mayotherwise set access restrictions. However, in some implementations, aportfolio record may not have restrictions placed on it by virtue ofbeing subordinate to another portfolio record.

In some implementations, the nested portfolio hierarchical informationmay specify that individual portfolio records are concurrentlysubordinate to more than one other portfolio record. This may bereferred to as multi-homing of a portfolio record. By way ofnon-limiting illustration, a third work unit record may be subordinateto a third project record, and the third project record maybesubordinate to a third portfolio record. The nested portfoliohierarchical information may specify that the second portfolio record issubordinate to the third portfolio record concurrently with beingsubordinate to the first portfolio record. Stated otherwise, the secondportfolio record may be considered multi-homed within the firstportfolio record and the third portfolio record. In the case ofmulti-homing, the presence of a multi-homed portfolio record in multipleother superior portfolio records may comprise separate instances of thesame portfolio record, albeit having access facilitated through thedifferent superior portfolio records.

In some implementations, the hierarchical information may specifyobjective record hierarchies. Individual sets of objective records maybe defined by an objective record hierarchy. An objective recordhierarchy may convey individual positions of objective records (andtheir corresponding business objectives) in the objective recordhierarchy. By way of non-limiting illustration, a position may specifyone or more of an objective record being superior to one or more otherobjective records, an objective record being subordinate to one or moreother objective records, and/or other information. As a result,individual objective records may be subordinate and/or superior to otherindividual objective records. An objective record may define a businessobjective comprising a progress towards fulfillment, and a subordinateobjective record may define a business objective comprising asubordinate progress towards fulfillment to the subordinate businessobjective. An objective record hierarchy may define a relationshipbetween objective records. In some implementations, as a consequence ofthe objective record hierarchies, the individual business objectivesdescribed in the individual objective records that are subordinate tothe other individual objective records may be subordinate to theindividual business objectives in the other individual objectiverecords.

The organization component 110 may be configured to determinepermissions information for portfolio records and/or other records. Thepermissions information may include values of permission parameters. Thepermissions parameters may characterize permissions with respect to howusers interact with the portfolio records, subordinate portfoliorecords, project records, work unit records, and/or other records. Thepermission parameters of the individual portfolio records maycharacterize access to the one or more of the project records that aresubordinate to the individual portfolio records. In someimplementations, access may be binary, including access being “granted”or access being “denied.” In some implementations, access may becharacterized by ability to navigate to and/or from one or more records.

In some implementations, permissions with respect to how users interactwith records may be characterized based on enabling and/or disabling oneor more features. Individual features may be related to the individualunits of work, the individual projects, and/or other individualportfolios. The features related to the individual units of work may bespecific to completing and/or supporting specific ones of the individualunits of work. The features related to the individual projects may bespecific to supporting the individual projects. The features related tothe individual portfolios may be specific to supporting the individualprojects that make up the individual portfolios (which may include thefeatures specific to supporting the individual projects), supporting theindividual units of work that make up the projects (which may includethe features specific to supporting the individual units of work),and/or other interactions. In some implementations, if one or morefeatures are not enabled for a given user, those one or more featuresmay be deemed disabled for the given user.

In some implementations, features specific to completing and/orsupporting the individual units of work may include one or more ofaccessing individual work unit pages for the individual units of work,specifying completion status of the individual units of work,communicating with other users linked within the individual units ofwork, generating meetings with the other users linked within theindividual units of work, accessing application programs outside of thecollaboration environment, editing the individual units of work, and/orother features.

In some implementations, specifying completion status of the individualunits of work may include the ability to change values of the workassignment parameter to indicate a unit of work has changed from“incomplete” to “marked complete” and/or “complete”. In someimplementations, specifying completion status of the individual units ofwork may include the ability to change values of the work assignmentparameter to indicate a unit of work has changed from “complete” or“marked complete” to “incomplete”.

In some implementations, communicating with other users linked withinthe individual units of work may include communicating within individualwork unit pages (e.g., adding comments, messages, and/or othercommunications), communicating within the collaboration environment(e.g., messaging system not tied to a given unit of work), communicatingoutside of the collaboration environment (e.g., email, SMS, etc.),and/or other considerations.

In some implementations, generating meetings with other users linked tothe individual units of work may include sending invites to the otherusers. Sending invites may include selecting meeting participants,proposed date/time for the meeting, setting agenda topics, and/or otherfunctionality. Meeting generation may be facilitated by functionalitythat is integral to the collaboration environment and/or providedthrough access to an external resource (e.g., third party meetinggeneration applications).

In some implementations, editing the individual units of work mayinclude one or more of adding, removing, changing, updating, and/orotherwise interacting directly with values of one or more work unitparameters of the individual units of work.

In some implementations, features specific to completing and/orsupporting the individual projects may be enabled within individualproject pages providing access to the individual projects. Theindividual sets of features specific to supporting the individualprojects may include one or more of accessing the individual projectpages, communicating with the other users within the individualprojects, generating meetings with the other users, editing theindividual projects, editing the units of work within the individualprojects, and/or other features.

In some implementations, communicating with the other users within theindividual projects may include communicating within individual projectpages (e.g., adding comments, messages, and/or other communications),communicating within the collaboration environment (e.g., messagingsystem not tied to a given project), communicating outside of thecollaboration environment (e.g., email, SMS, etc.), and/or otherconsiderations.

In some implementations, communicating with the other users linked tothe units of work within the individual projects may includecommunicating within individual work unit pages (e.g., adding comments,messages, and/or other communications), communicating within thecollaboration environment (e.g., messaging system not tied to a givenunit of work), communicating outside of the collaboration environment(e.g., email, SMS, etc.), and/or other considerations.

In some implementations, generating meetings with the other users linkedwithin the individual projects may include sending invites to the otherusers. Sending invites may include selecting meeting participants,proposed date/time for the meeting, setting agenda topics, and/or otherfunctionality.

In some implementations, generating meetings with the other users linkedto the units of work within the individual projects may include sendinginvites to the other users. Sending invites may include selectingmeeting participants, proposed date/time for the meeting, setting agendatopics, and/or other functionality. In some implementations, generatingmeetings with other users may be limited to other users having somelinking to one or more of the units of work that make up the project.

In some implementations, editing the individual projects may include oneor more of adding, removing, changing, updating, and/or otherwiseinteracting directly with values of one or more project parameters ofthe individual projects.

In some implementations, editing the units of work within the individualprojects may include one or more of adding, removing, changing,updating, and/or otherwise interacting directly with values of one ormore work unit parameters of the individual units of work within theproject.

In some implementations, the features available for individual units ofwork and/or individual projects that are subordinate to an individualportfolio may comprise the features of the individual portfolio itself.For example, the values of the permission parameters of the individualportfolio records may characterize access to one or more of the projectrecords that may be subordinate to the individual portfolio recordsand/or one or more work unit records that make up the one or moreproject records. However, other features specifically at the portfoliolevel may be provided. For example, features specifically at theportfolio level may include one or more of specifying another portfolioas being subordinate, adding projects to the portfolio, removingprojects from the portfolio, and/or other features.

In some implementations, sets of values of permission parameters of theindividual portfolio records may be determined based on the otherindividual ones of the portfolio records they are subordinate to. Thatis, adding a portfolio to an other portfolio may cause the portfolio totake on the values of the permission parameters of the other portfolio.Accordingly, features that may be enabled and/or disabled in a superiorportfolio record may be similarly enabled and/or disabled in asubordinate portfolio record. In some implementations adding and/orremoving a portfolio to and from another portfolio may be facilitated bydrag-and-drop input in a user interface, and/or other input.

By way of non-limiting illustration, the organization component 110 maybe configured to determine a first set of values of the permissionparameters for the second portfolio record in response to the secondportfolio records being subordinate to the first portfolio record. Thefirst set of values of permission parameters may be applied for thesecond portfolio record in response to the access of the secondportfolio record from the first portfolio page. By way of non-limitingillustration, the organization component 110 may be configured todetermine a second set of values of the permission parameters for thesecond portfolio record in response to the second portfolio recordsbeing subordinate to the third portfolio record. The second set ofvalues of the permission parameters may be applied for the secondportfolio record in response to the access of the second portfoliorecord from the third portfolio page. The first set of values may bedifferent from the second set of values by virtue of the nesting withinthe first portfolio record and third portfolio record, respectively.

The user interface component 112 may be configured to effectuatepresentation of user interfaces and/or other displays of thecollaboration environment on individual ones of the one or more clientcomputing platforms 104. The user interface component 112 may beconfigured to effectuate presentation of the collaboration environment,individual work unit pages of the collaboration environment, individualproject pages of the collaboration environment, individual portfoliopages of the collaboration environment, individual objective pages ofthe collaboration environment, and/or other content. The user interfacecomponent 112 may be configured to effectuate presentation of thecollaboration environment based on the environment state information sothat access, by the users, to one or more of the individual units ofwork, the individual projects, individual portfolios, and/or individualbusiness objectives reflects one or more of the hierarchicalinformation, permissions information, and/or other information.

In some implementations, user interface component 112 may be configuredto effectuate presentation of portfolio pages for the portfolio recordswithin a user interface of the collaboration environment. The individualportfolio pages for the individual portfolio records may provide accessto the individual project records, other individual portfolio records,and/or other records that may be subordinate to the individual portfoliorecords. By way of non-limiting illustration, a first portfolio page forthe first portfolio record may provide access to the first projectrecord that is subordinate to the first portfolio record, the secondportfolio record that is subordinate to the first portfolio record,and/or other content. In the case of multi-homing, a third portfoliopage for the third portfolio record may provide access to one or more ofthe third project record that is subordinate to the third portfoliorecord, to the second portfolio record that is subordinate to the thirdportfolio record, and/or other content. The access to the secondportfolio record via the third portfolio page may be separate anddistinct from the access to the second portfolio record via the firstportfolio page by virtue of utilizing separate instances of the secondportfolio record.

The individual portfolio pages for the individual portfolio records mayinclude individual user interface elements representing the individualproject records, the other individual portfolio records, and/or othercontent subordinate to the individual portfolio records. Users mayinteract with the portfolio pages through selection of the individualuser interface elements representing individual project records,individual portfolio records, and/or other content. The selection of auser interface element representing a project record may effectuatepresentation of a project page for the project record. The selection ofa user interface element representing a portfolio record may effectuatepresentation of a portfolio page for the portfolio record. In someimplementations, providing access to individual project records fromindividual superior portfolio records may include navigating away fromthe individual portfolio pages of the individual superior portfoliorecords to individual project pages of the individual subordinateproject records. In some implementations, providing access to theindividual subordinate portfolio records from individual superiorportfolio records includes navigating away from the individual portfoliopages of the individual superior portfolio records to other individualportfolio pages of the individual subordinate portfolio records.

User interface component 112 may be configured to provide access to(e.g., enable) and/or restrict access to (e.g., disable) features forthe users based on hierarchical information and its impact onpermissions information. User interface component 112 may be configuredto determine whether or not the users have a certain set of featuresenabled based on their navigation to one or more records from one ormore superior records.

In some implementations, user interface component 112 may be configuredto obtain input information and/or other information. The inputinformation may convey user input into a user interface presented on theclient computing platform(s) 104. A set of user interface elements maybe provided on the user interface to facilitate the user input and/orother user interaction with the user interface. The user interfaceelements may include one or more of text input fields, drop down menus,check boxes, display windows, virtual buttons, and/or other elementsconfigured to facilitate user interaction.

In some implementations, environment state information may be updated asusers continue to interact with the collaboration environment via theuser interfaces over time. The environment state component 108 may storeand/or archive the environment state information periodically and/orbased on user request to archive. In some implementations, theenvironment state component 108 may store historical environment stateinformation specifying historical user information, historical workinformation, historical project information, historical portfolioinformation, historical objective information, user interaction history,historical hierarchy information, and/or other information.

FIG. 3 illustrates a user interface 300 of a collaboration environment,in accordance with one or more implementations. The user interface 300may illustrate a nesting of portfolios within the collaborationenvironment, in accordance with one or more implementations. The userinterface 300 may present a portfolio page 302 for a portfolio 304(referred to as “Portfolio A”). Hierarchical information may specifythat one or more of a project record for a first project 308 (referredto as “Project X”) is subordinate to a portfolio record for theportfolio 304, a project record for a second project 310 (referred to as“Project Y”) is subordinate to the portfolio record for the portfolio304, and/or that a portfolio record for a second portfolio 306 (referredto as “Portfolio B”) is subordinate to the portfolio record for theportfolio 304. Permission information for one or more of the firstproject 308, the second project 310, and/or the second portfolio 306 maybe determined based on being subordinate to the portfolio 304.

The portfolio page 302 of the portfolio 304 may include individual userinterface elements representing individual ones of the first project308, the second project 310, and the second portfolio 306. Selection ofan individual user interface element may effectuate presentation ofrespective ones of the individual project pages for the individualproject records, and other individual portfolio pages for the otherindividual portfolio records.

FIG. 4 illustrates a user interface 400 of a collaboration environment,in accordance with one or more implementations. The user interface 400may present a second portfolio page 402 for the portfolio 306(“Portfolio B”). The second portfolio page 402 may be presented inresponse to selection of the user interface element representing thesecond portfolio 306 from user interface 300 of FIG. 3 . Hierarchicalinformation may specify that one or more of a project record for a thirdproject 404 (referred to as “Project W”) is subordinate to a portfoliorecord for the second portfolio 306, and/or a project record for afourth project 406 (referred to as “Project Z”) is subordinate to theportfolio record for the second portfolio 306. The user interface 400may include a user interface element 408 to facilitate navigation backto the project page 302 of FIG. 3 .

Referring back to FIG. 1 , in some implementations, server(s) 102,client computing platform(s) 104, and/or external resources 126 may beoperatively linked via one or more electronic communication links. Forexample, such electronic communication links may be established, atleast in part, via a network 116 such as the Internet and/or othernetworks. It will be appreciated that this is not intended to belimiting, and that the scope of this disclosure includes implementationsin which server(s) 102, client computing platform(s) 104, and/orexternal resources 126 may be operatively linked via some othercommunication media.

A given client computing platform may include one or more processorsconfigured to execute computer program components. The computer programcomponents may be configured to enable an expert or user associated withthe given client computing platform to interface with system 100 and/orexternal resources 126, and/or provide other functionality attributedherein to client computing platform(s) 104. By way of non-limitingexample, the given client computing platform 104 may include one or moreof a desktop computer, a laptop computer, a handheld computer, a tabletcomputing platform, a NetBook, a Smartphone, a gaming console, and/orother computing platforms.

External resources 126 may include sources of information outside ofsystem 100, external entities participating with system 100, and/orother resources. In some implementations, some or all of thefunctionality attributed herein to external resources 126 may beprovided by resources included in system 100.

Server(s) 102 may include electronic storage 128, one or more processors130, and/or other components. Server(s) 102 may include communicationlines, or ports to enable the exchange of information with a network 116and/or other computing platforms. Illustration of server(s) 102 in FIG.1 is not intended to be limiting. Server(s) 102 may include a pluralityof hardware, software, and/or firmware components operating together toprovide the functionality attributed herein to server(s) 102. Forexample, server(s) 102 may be implemented by a cloud of computingplatforms operating together as server(s) 102.

Electronic storage 128 may comprise non-transitory storage media thatelectronically stores information. The electronic storage media ofelectronic storage 128 may include one or both of system storage that isprovided integrally (i.e., substantially non-removable) with server(s)102 and/or removable storage that is removably connectable to server(s)102 via, for example, a port (e.g., a USB port, a firewire port, etc.)or a drive (e.g., a disk drive, etc.). Electronic storage 128 mayinclude one or more of optically readable storage media (e.g., opticaldisks, etc.), magnetically readable storage media (e.g., magnetic tape,magnetic hard drive, floppy drive, etc.), electrical charge-basedstorage media (e.g., EEPROM, RAM, etc.), solid-state storage media(e.g., flash drive, etc.), and/or other electronically readable storagemedia. Electronic storage 128 may include one or more virtual storageresources (e.g., cloud storage, a virtual private network, and/or othervirtual storage resources). Electronic storage 128 may store softwarealgorithms, information determined by processor(s) 130, informationreceived from server(s) 102, information received from client computingplatform(s) 104, and/or other information that enables server(s) 102 tofunction as described herein.

Processor(s) 130 may be configured to provide information processingcapabilities in server(s) 102. As such, processor(s) 130 may include oneor more of a digital processor, a physical processor, an analogprocessor, a digital circuit designed to process information, an analogcircuit designed to process information, a state machine, and/or othermechanisms for electronically processing information. Althoughprocessor(s) 130 is shown in FIG. 1 as a single entity, this is forillustrative purposes only. In some implementations, processor(s) 130may include a plurality of processing units. These processing units maybe physically located within the same device, or processor(s) 130 mayrepresent processing functionality of a plurality of devices operatingin coordination. Processor(s) 130 may be configured to executecomponents 108, 110, 112, and/or other components. Processor(s) 130 maybe configured to execute components 108, 110, and/or 112, and/or othercomponents by software; hardware; firmware; some combination ofsoftware, hardware, and/or firmware; and/or other mechanisms forconfiguring processing capabilities on processor(s) 130. As used herein,the term “component” may refer to any component or set of componentsthat perform the functionality attributed to the component. This mayinclude one or more physical processors during execution of processorreadable instructions, the processor readable instructions, circuitry,hardware, storage media, or any other components.

It should be appreciated that although components 108, 110, and/or 112are illustrated in FIG. 1 as being implemented within a singleprocessing unit, in implementations in which processor(s) 130 includesmultiple processing units, one or more of components 108, 110, and/or112 may be implemented remotely from the other components. Thedescription of the functionality provided by the different components108, 110, and/or 112 described below is for illustrative purposes, andis not intended to be limiting, as any of components 108, 110, and/or112 may provide more or less functionality than is described. Forexample, one or more of components 108, 110, and/or 112 may beeliminated, and some or all of its functionality may be provided byother ones of components 108, 110, and/or 112. As another example,processor(s) 130 may be configured to execute one or more additionalcomponents that may perform some or all of the functionality attributedbelow to one of components 108, 110, and/or 112.

FIG. 2 illustrates a method 200 to facilitate nesting of portfolioswithin a collaboration environment, in accordance with one or moreimplementations. The operations of method 200 presented below areintended to be illustrative. In some implementations, method 200 may beaccomplished with one or more additional operations not described,and/or without one or more of the operations discussed. Additionally,the order in which the operations of method 200 are illustrated in FIG.2 and described below is not intended to be limiting.

In some implementations, method 200 may be implemented in one or moreprocessing devices (e.g., a digital processor, an analog processor, adigital circuit designed to process information, an analog circuitdesigned to process information, a state machine, and/or othermechanisms for electronically processing information). The one or moreprocessing devices may include one or more devices executing some or allof the operations of method 200 in response to instructions storedelectronically on an electronic storage medium. The one or moreprocessing devices may include one or more devices configured throughhardware, firmware, and/or software to be specifically designed forexecution of one or more of the operations of method 200.

An operation 202 may manage environment state information maintaining acollaboration environment. The collaboration environment may beconfigured to facilitate interaction by users with the collaborationenvironment. The environment state information may include one or moreof work unit records, project records, portfolio records, and/or otherrecords. The work unit records may include work unit informationassociated with units of work managed, created, and/or assigned withinthe collaboration environment, and/or other information. The projectrecords may include project information associated with projectsmanaged, created, and/or assigned within the collaboration environment,and/or other information. The portfolio records may include portfolioinformation associated with portfolios managed within the collaborationenvironment, and/or other information. Operation 202 may be performed byone or more hardware processors configured by machine-readableinstructions including a component that is the same as or similar toenvironment state component 108 (shown in FIG. 1 and described herein),in accordance with one or more implementations.

An operation 204 may obtain hierarchical information for the work unitrecords, the project records, and the portfolio records. Thehierarchical information may specify individual work unit records assubordinate to individual project records, and/or the individual projectrecords as subordinate to individual portfolio records. By way ofnon-limiting illustration, an individual project record may include oneor more work unit records by virtue of the one or more work unit recordsbeing subordinate to the individual project record. By way ofnon-limiting illustration, an individual portfolio record may includeone or more project records by virtue of the one or more project recordsbeing subordinate to the individual portfolio record. By way ofnon-limiting illustration, a first work unit record may be subordinateto a first project record, and the first project record may besubordinate to a first portfolio record. Operation 204 may be performedby one or more hardware processors configured by machine-readableinstructions including a component that is the same as or similar toorganization component 110 (shown in FIG. 1 and described herein), inaccordance with one or more implementations.

An operation 206 may obtain and/or specify nested portfolio hierarchicalinformation specific to the portfolio records. The nested portfoliohierarchical information may specify the individual portfolio records asbeing subordinate to other individual ones of the portfolio records. Byway of non-limiting illustration, the nested portfolio hierarchicalinformation may specify a second portfolio record as being subordinateto the first portfolio record. Operation 206 may be performed by one ormore hardware processors configured by machine-readable instructionsincluding a component that is the same as or similar to organizationcomponent 110 (shown in FIG. 1 and described herein), in accordance withone or more implementations.

An operation 208 may effectuate presentation of portfolio pages for theportfolio records within a user interface of the collaborationenvironment. Individual portfolio pages for the individual portfoliorecords may provide access to the individual project records and otherindividual portfolio records that are subordinate to the individualportfolio records. By way of non-limiting illustration, a firstportfolio page for the first portfolio record may provide access to oneor more of the first project record that is subordinate to the firstportfolio record, the second portfolio record that is subordinate to thefirst portfolio record, and/or other records. Operation 208 may beperformed by one or more hardware processors configured bymachine-readable instructions including a component that is the same asor similar to user interface component 112 (shown in FIG. 1 anddescribed herein), in accordance with one or more implementations.

Although the present technology has been described in detail for thepurpose of illustration based on what is currently considered to be themost practical and preferred implementations, it is to be understoodthat such detail is solely for that purpose and that the technology isnot limited to the disclosed implementations, but, on the contrary, isintended to cover modifications and equivalent arrangements that arewithin the spirit and scope of the appended claims. For example, it isto be understood that the present technology contemplates that, to theextent possible, one or more features of any implementation can becombined with one or more features of any other implementation.

What is claimed is:
 1. A method to provide access to portfolio recordsof portfolios managed within a collaboration environment, the methodcomprising: managing environment state information maintaining acollaboration environment, the collaboration environment beingconfigured to facilitate interaction by users with the collaborationenvironment, the environment state information including work unitrecords, project records, and portfolio records, the work unit recordsincluding work unit information associated with units of work managed,created, and/or assigned within the collaboration environment, theproject records including project information associated with projectsmanaged, created, and/or assigned within the collaboration environment,and the portfolio records including portfolio information associatedwith portfolios managed within the collaboration environment; obtaininghierarchical information for the work unit records, the project records,and the portfolio records, the hierarchical information specifyingindividual work unit records as subordinate to individual projectrecords, and the individual project records as subordinate to individualportfolio records, such that an individual project record is associatedwith one or more of the work unit records by virtue of the one or moreof the work unit records being subordinate to the individual projectrecord, and wherein an individual portfolio record is associated withone or more of the project records by virtue of the one or more of theproject records being subordinate to the individual portfolio record,wherein a first work unit record is subordinate to a first projectrecord, and the first project record is subordinate to a first portfoliorecord; specifying nested portfolio hierarchical information specific tothe portfolio records, wherein the nested portfolio hierarchicalinformation specifies the individual portfolio records as beingsubordinate to other individual ones of the portfolio records, such thatthe nested portfolio hierarchical information specifies a secondportfolio record as being subordinate to the first portfolio record; andeffectuating presentation of portfolio pages for the portfolio recordswithin a user interface of the collaboration environment, individualportfolio pages for the individual portfolio records providing access tothe individual project records and other individual portfolio recordsthat are subordinate to the individual portfolio records as specified bythe nested portfolio hierarchical information, such that a firstportfolio page for the first portfolio record provides access to thefirst project record that is subordinate to the first portfolio record,and provides access to the second portfolio record that is subordinateto the first portfolio record.
 2. The method of claim 1, wherein thenested portfolio hierarchical information specifies the individualportfolio records as being concurrently subordinate to more than oneother portfolio record, such that: a third work unit record issubordinate to a third project record, and the third project record issubordinate to a third portfolio record; the nested portfoliohierarchical information specifies the second portfolio record as beingsubordinate to the third portfolio record concurrently with beingsubordinate to the first portfolio record; and a third portfolio pagefor the third portfolio record provides access to the third projectrecord that is subordinate to the third portfolio record, and providesaccess to the second portfolio record that is subordinate to the thirdportfolio record, the access to the second portfolio record via thethird portfolio page being separate and distinct from the access to thesecond portfolio record via the first portfolio page.
 3. The method ofclaim 1, wherein providing access to the individual project recordsincludes navigating away from the individual portfolio pages toindividual project pages of the individual project records; and whereinproviding access to the other individual portfolio records includesnavigating away from the individual portfolio pages to other individualportfolio pages of the other individual portfolio records.
 4. The methodof claim 3, wherein the individual portfolio pages for the individualportfolio records include individual user interface elementsrepresenting the individual project records and the other individualportfolio records that are subordinate to the individual portfoliorecords, wherein selection of the individual user interface elementsrepresenting the individual project records effectuates presentation ofthe individual project pages for the individual project records, andwherein selection of the individual user interface elements representingthe other individual portfolio records effectuates presentation of theother individual portfolio pages for the other individual portfoliorecords.
 5. The method of claim 1, further comprising determiningdifferent sets of values of permission parameters of the individualportfolio records based on the other individual ones of the portfoliorecords they are subordinate to, including: determining a first set ofvalues of the permission parameters for the second portfolio record inresponse to the second portfolio record being subordinate to the firstportfolio record, the first set of values of permission parameters beingapplied in response to the access of the second portfolio record fromthe first portfolio page; and determining a second set of values of thepermission parameters for the second portfolio record in response to thesecond portfolio record being subordinate to the third portfolio record,the second set of values of the permission parameters being applied inresponse to the access of the second portfolio record from the thirdportfolio page.
 6. The method of claim 5, wherein the values of thepermission parameters of the individual portfolio records characterizeaccess to the one or more of the project records that are subordinate tothe individual portfolio records, such that the access is either grantedor denied.
 7. The method of claim 6, wherein the access is characterizedby ability to navigate through the collaboration environment.
 8. Themethod of claim 5, wherein the values of the permission parameters ofthe individual portfolio records characterize availability of featuresrelated to the individual units of work, the individual projects, andthe individual portfolio records.
 9. The method of claim 8, wherein thefeatures related to the individual units of work are specific tocompleting and/or supporting the individual units of work, the featuresrelated to the individual projects are specific to supporting theindividual projects, the features related to the individual portfoliosare portfolio-level features.
 10. The method of claim 9, wherein thefeatures include one or more of specifying completion, communicatingwithin the collaboration environment, communicating outside thecollaboration environment, generating meetings, accessing applicationprograms, or editing.
 11. A system configured to provide access toportfolio records of portfolios managed within a collaborationenvironment, the system comprising: one or more physical processors; anda computer-readable medium storing machine-readable instructions that,when executed by the one or more physical processors, cause the systemto perform operations comprising: manage environment state informationmaintaining a collaboration environment, the collaboration environmentbeing configured to facilitate interaction by users with thecollaboration environment, the environment state information includingwork unit records, project records, and portfolio records, the work unitrecords including work unit information associated with units of workmanaged, created, and/or assigned within the collaboration environment,the project records including project information associated withprojects managed, created, and/or assigned within the collaborationenvironment, and the portfolio records including portfolio informationassociated with portfolios managed within the collaboration environment;obtain hierarchical information for the work unit records, the projectrecords, and the portfolio records, the hierarchical informationspecifying individual work unit records as subordinate to individualproject records, and the individual project records as subordinate toindividual portfolio records, such that an individual project record isassociated with one or more of the work unit records by virtue of theone or more of the work unit records being subordinate to the individualproject record, and wherein an individual portfolio record is associatedwith one or more of the project records by virtue of the one or more ofthe project records being subordinate to the individual portfoliorecord, wherein a first work unit record is subordinate to a firstproject record, and the first project record is subordinate to a firstportfolio record; specify nested portfolio hierarchical informationspecific to the portfolio records, wherein the nested portfoliohierarchical information specifies the individual portfolio records asbeing subordinate to other individual ones of the portfolio records,such that the nested portfolio hierarchical information specifies asecond portfolio record as being subordinate to the first portfoliorecord; and effectuate presentation of portfolio pages for the portfoliorecords within a user interface of the collaboration environment,individual portfolio pages for the individual portfolio recordsproviding access to the individual project records and other individualportfolio records that are subordinate to the individual portfoliorecords as specified by the nested portfolio hierarchical information,such that a first portfolio page for the first portfolio record providesaccess to the first project record that is subordinate to the firstportfolio record, and provides access to the second portfolio recordthat is subordinate to the first portfolio record.
 12. The system ofclaim 11, wherein the nested portfolio hierarchical informationspecifies the individual portfolio records as being concurrentlysubordinate to more than one other portfolio record, such that: a thirdwork unit record is subordinate to a third project record, and the thirdproject record is subordinate to a third portfolio record; the nestedportfolio hierarchical information specifies the second portfolio recordas being subordinate to the third portfolio record concurrently withbeing subordinate to the first portfolio record; and a third portfoliopage for the third portfolio record provides access to the third projectrecord that is subordinate to the third portfolio record, and providesaccess to the second portfolio record that is subordinate to the thirdportfolio record, the access to the second portfolio record via thethird portfolio page being separate and distinct from the access to thesecond portfolio record via the first portfolio page.
 13. The system ofclaim 11, wherein providing access to the individual project recordsincludes navigating away from the individual portfolio pages toindividual project pages of the individual project records; and whereinproviding access to the other individual portfolio records includesnavigating away from the individual portfolio pages to other individualportfolio pages of the other individual portfolio records.
 14. Thesystem of claim 13, wherein the individual portfolio pages for theindividual portfolio records include individual user interface elementsrepresenting the individual project records and the other individualportfolio records that are subordinate to the individual portfoliorecords, wherein selection of the individual user interface elementsrepresenting the individual project records effectuates presentation ofthe individual project pages for the individual project records, andwherein selection of the individual user interface elements representingthe other individual portfolio records effectuates presentation of theother individual portfolio pages for the other individual portfoliorecords.
 15. The system of claim 11, wherein execution of themachine-readable instructions by the one or more physical processorsfurther cause the system to perform an operation of: determine differentsets of values of permission parameters of the individual portfoliorecords based on the other individual ones of the portfolio records theyare subordinate to, including: determining a first set of values of thepermission parameters for the second portfolio record in response to thesecond portfolio record being subordinate to the first portfolio record,the first set of values of permission parameters being applied inresponse to the access of the second portfolio record from the firstportfolio page; and determining a second set of values of the permissionparameters for the second portfolio record in response to the secondportfolio record being subordinate to the third portfolio record, thesecond set of values of the permission parameters being applied inresponse to the access of the second portfolio record from the thirdportfolio page.
 16. The system of claim 15, wherein the values of thepermission parameters of the individual portfolio records characterizeaccess to the one or more of the project records that are subordinate tothe individual portfolio records, such that the access is either grantedor denied.
 17. The system of claim 16, wherein the access ischaracterized by ability to navigate through the collaborationenvironment.
 18. The system of claim 15, wherein the values of thepermission parameters of the individual portfolio records characterizeavailability of features related to the individual units of work, theindividual projects, and the individual portfolio records.
 19. Thesystem of claim 18, wherein the features related to the individual unitsof work are specific to completing and/or supporting the individualunits of work, the features related to the individual projects arespecific to supporting the individual projects, the features related tothe individual portfolios are portfolio-level features.
 20. The systemof claim 19, the features include one or more of specifying completion,communicating within the collaboration environment, communicatingoutside the collaboration environment, generating meetings, accessingapplication programs, or editing.